Automated on-line commerce method and apparatus utilizing a shopping server verifying product information on product selection

ABSTRACT

An on-line commerce method and apparatus. A user can select products for purchase from plural merchant servers by examining product information stored on a shopping server. The product information related to selected products is verified by accessing a checkout page of each merchant server. The verified information is then presented to the user for confirmation. Upon confirmation, buy procedures are executed on each merchant server to purchase the products using existing account information for the user at each merchant server.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to systems for the purchase of goods and servicesover a communications network. More specifically, the invention is anautomated purchase support method and apparatus for seamlesslyintegrating plural merchants into an on-line shopping system.

2. Description of the Related Art

The Internet is a worldwide network of computers linked together byvarious hardware communication links all running a standard suite ofprotocols known as TCP/IP (transmission control protocol/Internetprotocol). The growth of the Internet over the last several years hasbeen explosive, fueled in the most part by the widespread use ofsoftware viewers known as browsers and HTTP (hypertext transferprotocol) which allow a simple GUI (graphical user interface) to be usedto communicate over the Internet. Browsers generally reside on thecomputer used to access content on the Internet, i.e. the clientcomputer. HTTP is a component of TCP/IP and provides users access tofiles of various formats using a standard page description languageknown as HTML (hypertext markup language), and more recently XML(extensible markup language) and XHTML (extensible hypertext markuplanguage), a reformulation of HTML into XML. The collection of serverson the Internet using HTTP has become known as the “World Wide Web” orsimply the “Web.”

Through HTML, XHTML, and interactive programming protocols, the authorof a particular Web page is able to make information available toviewers of the Web page by placing the Web page on an Internet Webserver. The network path to the server is identified by a URL (UniformResource Locator) and, generally, any client running a Web browser canaccess the Web server by using the URL. A client computer running abrowser can request a display of a Web page stored on a Web server byissuing a URL request through the Internet to the Web in a known manner.A URL consistent with the present invention may be a simple URL of theform:

<protocol identifiers>://<server path>/<web page path>

A “protocol identifier” of “http” specifies the conventional hyper-texttransfer protocol. A URL request for a secure Internet transactiontypically utilizes the secure protocol identifier “https,” assuming thatthe browser running on the client and the Web server control programrunning on the Web server support and implement the secure sockets layerdiscussed below. The “server path” is typically of the form“prefix.domain,” where the prefix is typically “www” to designate a Webserver and the “domain” is the standard Internetsub-domain.top-level-domain of the Web server. The optional “web pagepath” is provided to specifically identify a particular hyper-text pagemaintained on the Web server. In response to a received URL identifyingan existing Web page, the Web server can return the Web page, subject tothe HTTP protocol, to the client computer for display on the clientcomputer. Such a Web page typically incorporates both textural andgraphical information including embedded hyper-text links that permitthe user of the client computer to readily select a next URL or sendother data over the Internet. Further, a Web page can have embeddedapplets, written in Java™ or another programming language, to presentanimation and/or audio.

The URL issued from the client computer may also be of a complex formthat identifies a CGI (common gateway interface) program (or script) onthe Web server. The CGI program permits interactivity between the clientcomputer and the Web server via HTTP. CGI is a standard for externalgateway programs to interface with information servers, such as Webservers. A plain HTML document that the Web server delivers issubstantially static. A CGI program, on the other hand, is executed inreal-time so that it can process data or execute commands, such asexecuting a buy procedure which authorizes a purchase of productsthrough a commerce Web server. A HTML form definition reference thatidentifies a CGI program is commonly of the form:

<form action-http://www.vendor.com/cgi-bin/buy.cgi method=post>

A hyper-text link of this form directs the execution of the buy.cgiprogram on the Web server in response to a command from the clientcomputer. For example, buy.cgi can be a buy procedure of the Web server.The Web has become ubiquitous in businesses and homes because it hasproven to be convenient for various applications, such as news and datadelivery, conducting banking and investment transactions, and the like.The Web and its authoring, transmission, and display protocols, such asbrowsers, HTML, CGI, Active Server Pages™, and Java™, have become aworldwide standard for information exchange.

One of the primary applications of the Web has been shopping, i.e. thepurchase of goods and services, i.e. products. Virtually every majorcommercial “bricks and mortar” merchant has established a Web site forthe showcase and sale of their products. Further many manufacturers sellproducts directly over the Web. Finally, a plethora of on-linemerchants, not previously existing in the bricks and mortar world, havecome into existence. As a result, virtually every product is availablefor purchase over the Web from a plurality of merchants. This situationhas increased the efficiency of markets by permitting shoppers toreadily compare products and terms of sale from plural merchants withoutthe need to travel physically to the merchant locations.

However, in order to compare products and terms of different merchants,one must “visit” the various merchant web sites individually. First,this requires knowledge of the URLs for each merchant Web site or theuse of a search engine which can be cumbersome and inaccurate. It ispossible to open the various sites in different browser windows forbetter comparison. However, the various formats of each merchant Website render it tedious to compare products and terms directly. When apurchase decision is made, the purchase or purchases must be madethrough the individual merchant Web sites. Further, ordinarily theshopper is required to log in to each merchant Web site, by entering ausername and password for example, prior to making a purchase and thenproceed to the next site. For example, if the shopper decides to buythree items from three different merchants, three log in procedures andthree buy procedures, i.e. procedures for effecting a purchase on themerchant Web sites, must be manually executed respectively through thethree merchant Web sites and their proprietary interfaces.

Recently, it is known to integrate a plurality of web sites into asingle environment known as a “shopping portal.” Shopping portalsordinarily include a Web server presenting an integrated interfacedisplaying plural products from various merchants. Accordingly,conventional shopping portals facilitate comparison shopping and thusincrease market efficiency. However, conventional shopping portalsmerely serve as a gateway to the individual merchant Web sites. Inparticular, when a purchasing decision is made, the shopper is directedto the merchant Web site and the purchase is completed manually throughthe merchant Web site using the merchant Web site buy procedures andinterface. Accordingly, when purchases are made from more than onemerchant, conventional shopping portals require that the shopper executethe orders using different interfaces at the respective merchant Websites.

U.S. Pat. No. 5,895,454 discloses an interface for merchant Web sites. Ashopper connects to a remote merchant Web site through a shoppingserver. When a product is selected from a merchant server, a transactionnotification is transmitted to a database on the shopping server. Whenthe shopper is finished shopping, the shopper server transmits purchaseorders corresponding to the selected products to the merchant web sitesto complete the orders on behalf of the shopper. However, the systemdisclosed in U.S. Pat. No. 5,895,454 requires that the shopper navigateeach merchant Web site individually to select products for purchase.

SUMMARY OF THE INVENTION

It is an object of the invention to seamlessly integrate plural on-linemerchants into a single shopping interface.

It is another object of the invention to facilitate comparison shoppingin an on-line environment.

It is another object of the invention to retain individual merchantaccounts while permitting purchasing from plural merchants through asingle on-line interface.

It is another object of the invention to permit a shopper to retain theadvantages of shopping at a merchant site while using an integratedshopping interface.

It is another object of the invention to permit a merchant site toobtain all the commercial advantages of an actual visit by a shopperwhile facilitating shopping from plural merchant sites.

To achieve these and other objects, a first aspect of the invention ismethod of effecting commerce in a networked computer environmentcomprising the steps of identifying a user of a client computer to ashopping server having a database, selecting a product, based on productinformation in the database, for purchase from a merchant server that isremote from the shopping server, verifying the product informationrelated to the selected product by communicating updated informationrelated to the selected product from the merchant server to the shoppingserver, presenting verified product information to the user forconfirmation of a purchase, and executing a buy procedure on themerchant server for purchase of the selected products from the merchantserver if the user confirms the purchase.

A second aspect of the invention is a computer architecture foreffecting commerce in a networked environment comprising a clientcomputer, a shopping server executing an agent application and includinga memory device having a database stored therein, a merchant serverexecuting a commerce server application and being remote from theshopping server, and a communication channel coupling the merchantserver with the shopping server and the shopping server with the clientcomputer. The agent application is operative to identify a user of theclient computer to the shopping server, permit the user to select aproduct, based on product information in the database, for purchase fromthe merchant server, verify the product information related to theselected product by communicating updated information related to theselected product from the merchant server to the shopping server overthe communication channel, present verified product information to theuser for confirmation of a purchase, and execute a buy procedure on themerchant server for purchase of the selected products from the merchantserver if the user confirms the purchase.

BRIEF DESCRIPTION OF THE DRAWING

The invention is described through a preferred embodiment and theattached drawing in which:

FIG. 1 is a block diagram of a computer architecture in accordance witha preferred embodiment of the invention;

FIG. 2 is a block diagram of a portion of the architecture of FIG. 1schematically illustrating the communication channel connections for anautomated purchase procedure;

FIG. 3 is a block diagram of the cookie handling procedure of thepreferred embodiment; and

FIG. 4 is a schematic representation of the internal automated purchaseprocedure of the shopping server of the preferred embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

A preferred embodiment of a computer architecture of the invention isillustrated in FIG. 1. Commerce system 10 includes client computer 12executing browser application 14 that supports the HTTP protocol. Clientcomputer 12 is connected, typically through an ISP (Internet ServiceProvider), to Internet 100 serving as a communication channel. Forexample, client computer system 12 can be coupled to the ISP via aconventional dial up connection using a modem or through a broadbandconnection such as ISDN (Integrated Services Digital Network), a cablemodem, or a DSL (Digital Subscriber Line) connection. Shopping server 20is also coupled to Internet 100 in a known manner. Shopping server 20executes a Web server control application 22, known as an HTTP serverapplication, stored in a memory device. For example, public domain webserver software applications from NCSA or APACHE can be used.

Shopping server 20 also executes agent server control application 24,(the function of which is described in detail below) utilizing a secureconnection for privacy. Agent server control application 24 can utilizeSSL (secure sockets layer), S-HTTP (secure HTTP), or any other type ofsecure connection (standard protocols for transmitting private documentsvia the internet). SSL works by using a private key to encrypt data thatis transferred over the SSL connection. It is common for Web sites touse SSL to obtain confidential user information, such as credit cardnumbers. As noted above, Web pages that require an SSL connection have aURL starting with “https:” instead of “http:.” Whereas SSL creates asecure connection between a client and a server over which any amount ofdata can be sent securely, S-HTTP is designed to transmit individualmessages securely.

A plurality of merchant servers 40 provide on-line shopping usingconventional commerce server control applications, i.e. software thatruns some of the main functions of an online storefront such as productdisplay, online ordering, and inventory management. Merchant servers 40and commerce server software are well known and thus are not describedin detail herein.

In the preferred embodiment, each of client computer 12, shopping server20, and merchant servers 40 are capable of communicating using a secureconnection protocol, such as SSL or S-HTTP. For clarity, non secureconnections 30 and secure connections 32 are illustrated separately.However, typically, these connections will be effected over the samephysical connection or communication channel, such as Internet 100.Further, shopping server 20 and merchant servers 40 can have many Webpages stored in memory devices thereof as files in HTML format and/orother formats. Shopping server 20 also includes product database 26 andshopper database 28 stored in a memory device thereof as described indetail below.

Client computer 12 can request a display of a Web page stored onshopping server 20 by issuing a URL request through Internet 100 toshopping server 20. For example, a user of client computer 12, i.e. ashopper, can select a product, or plural products, for purchase bynavigating Web pages stored on shopping server 20 and populated withproduct information from product database 26. Product database 26 caninclude product descriptions, pricing, delivery dates, and other productinformation for plural merchants and culled from merchant servers 40using automated Web crawlers or “bots” or gathered in any other manner.The product information in product database 26 should be updatedperiodically to correspond with current product information on merchantservers 40. However, as will become apparent below, the productinformation need not be updated in real time.

The product information can be searched and displayed by product type,part numbers, price, keywords, or product features in any desirablemanner using an interface of shopping server 20 as presented to theshopper by browser application 14 on client computer 12. The productinformation in product data base 26 relating to products from pluralmerchant servers 40 can be displayed side by side in the browser windowof client computer 12 to permit the shopper to comparison shop andchoose products from any one or more of merchant servers 40 based on theproduct information. For example, the user may search for all instancesof a particular item by product name or part number and may select forpurchase the instance from the merchant having the lowest price. Forexample, the shopping interface known as SMARTSHOP.COM™ can be used inconnection with the invention. Upon logging in to shopping server 20, byentering a username and user id as identification data for example, auser can be identified and thus can avoid the need for reenteringpreviously registered data and preferences.

FIG. 2 schematically illustrates the communications channel connectionsof the preferred embodiment during an automated purchasing procedure.For the sake of clarity, the remaining description refers generally toonly one merchant server 40. However, it should be understood that theprocedure described below can be accomplished for plural products fromplural merchant servers 40. When a user selects a product for purchase,by clicking on a “buy” button for example, secure connection 32 isestablished between client computer 12 and agent server application 24of shopping server 20. Agent server application 24 then opens parallelsecure connection 32 with the commerce server application of merchantserver 40. Secure connections 32 are illustrated as direct connectionsbetween computers for clarity. However, it should be understood thatsecure connections 32 can be SSL connections over Internet 100 or anyother type of communication channel.

Also, as illustrated in FIG. 2, first “cookie” 29 (i.e. a filecontaining information, such as identification information, to be usedby a server) is established on shopping server 20 and second cookie 18is established on client computer 12. First cookie 29 allows merchantserver 40 to track status of its order acceptance process and secondcookie 18 allows shopping server 20 to track status of its orderplacement process. With reference to FIG. 3, first cookie 29 containsinformation identifying the order acceptance session between shoppingserver 20 and merchant server 40, i.e. a merchant session ID. Theidentifying information can be any character string or code by whichmerchant server 40 can identify the order acceptance session. Similarly,second cookie 18 contains a “nonce” (i.e. a one-time random string), orother information identifying the order placement session between clientcomputer 12 and shopping server 20. Shopping server 20 maintains record55, such as a database or a lookup table, that associates the nonce ofsecond cookie 18 with the corresponding transaction record 54 (seedescription of FIG. 4 below), by pointing to the transaction record 54for example. Changes in transaction reporting from merchant server 40are recorded in transaction record 54 because the two are synchronizedby virtue of pointers from the nonces to transaction record 54.Transaction record 54 also contains the corresponding merchant sessionID. Accordingly, when the shopper resumes an idle session, such as byconfirming an order through client computer 12, shopping server 20examines second cookie 18 and identifies the corresponding orderplacement session and status and is thus able to resume the session in asecure manner. Further, shopping server 20 will locate the correspondingfirst cookie 29 and present it to merchant server 40 to resume thecorresponding order acceptance session.

Keep in mind that there typically are a plurality of order placement andcorresponding order acceptance sessions occurring simultaneously. Thecookie management procedure described above allows all sessions to becorrelated properly and thus permits a seamless shopping experience.Shopping server 20 uses information stored in shopper database 28 to acton the shopper's behalf during execution of a buy procedure of merchantserver 40. Shopper database 28 can include any appropriate informationabout registered shoppers, such as their name, address, shoppingpreferences, credit card numbers, merchant account information (such asa username and user id for the shopper at each particular merchant), andthe like. Of course all data in shopper database 28 can be collectedduring a registration procedure and encrypted for security in a knownmanner.

FIG. 4 illustrates the purchase procedure, i.e. the function of agentserver 24, of shopping server 20 in greater detail. Keep in mind thatthe purchase procedure ordinarily begins after the shopper has logged into shopping server 20 or otherwise identified themselves uniquely. Thefirst phase of the purchase procedure permits the shopper to searchproducts, browse for products in various ways, and select one or moreproducts for purchase from one or more merchant servers 40. Afterlogging in, main process 50 of agent server control application 24generates buy form 52 for display to the shopper. In the event that theshopper desires to change information in buy form 52 for the currentpurchase procedure, the shopper can merely edit buy form 52. Forexample, the shopper may wish to change the shipping address or shipmentmethod. Of course, the shopper profile can be edited to change thedefault shopper information in shopper database 28. Buy form 52 isautomatically pre-filled with default shopper information correspondingto the shopper if such information exists as a shopper profile inshopper database 28. If such information does not exist for the shopper,the shopper can be prompted to enter the information and the informationcan be used in the current purchase procedure. Main process 52 alsocreates transaction record 54 which keeps track of all transactioninformation, including transaction status, for the current transactionprocedure (such as credit card information, billing addresses, and thelike from shopper database 28 and merchant SKUs of selected products,shipping options, and the like from product database 26).

Also, main process 50 spawns buy process 56 and points buy process 56 tothe corresponding transaction record. As the shopper selects variousproducts and options using the browser interface of client computer 12,transaction record 54 is updated. Note that, at any given time, therecan be plural purchase procedures for plural shoppers each having arespective buy process 56 and corresponding transaction record 54. Buyprocess 56 will continue to run in parallel with main process 50 untilthe purchase procedure is completed. Buy process 56 continually updatestransaction record 54 based on shopper selections. Meanwhile, mainprocess 50 polls transaction record 54 for updated status. In thismanner, main process 50 is updated with the status of each purchaseprocedure.

When the first phase of the purchase procedure is complete, i.e. theshopper has selected all desired products and options from all desiredmerchants, main process 50 presents confirmation page 58 to the shopper,through the browser interface of client computer system 12, forverification of an order by the shopper. Confirmation page 58 isgenerated by communication between shopping server computer system 20and the appropriate merchant server 40 using secure connection 32between shopping server computer system 20 and the appropriate merchantserver 40. In particular, shopping server computer system 20 uses theinformation in transaction record 54 to verify pricing information,shipping information, and other details of the desired purchase withmerchant server 40 by automatically going to each merchant checkoutpage, or other information page, and retrieving the updated information.Buy procedures of merchant server 40 are integrated into buy processesof shopping server 20 to allow buy process 56 to automatically navigatemerchant server 40. Back end test scripts or the like can be used todetermine the particular buy procedure steps of merchant server 40.

If account information for a particular merchant exists for the shopperin shopper database 28, that account information is used when executingthe buy procedures with the merchant server 40. If not, a new account iscreated for the shopper with the merchant and the account information isstored in shopper database 28 for subsequent use. Since shopping server20 uses merchant account information that corresponds to the shopper,the shopper can retain preferred buyer points and other benefits anddiscounts as if shopping directly at merchant server 40.

Keep in mind that, in the preferred embodiment, up to the time ofgenerating confirmation page 58 communication has been between clientcomputer system 12 and shopping server 20 using information from productdatabase 26, which might not be entirely updated due to the fluid stateof on-line commerce. Accordingly, confirmation page 58 includesreal-time pricing and shipping information obtained from merchant server40 for each selected product in transaction record 54. Upon receivingshopper confirmation of the order summarized in confirmation page 58,all transaction information in transaction record 54 is saved and secondcookie 18 is saved to allow the procedure to restart later on with thesame user session. Buy process 56 remains idle while waiting for theshopper to confirm the order by selecting a button on confirmation page58 or taking other action.

In the second phase of the purchase procedure, the purchase transactionis completed. In particular, second cookie 18 is used to resume theprevious user session on merchant server 40. Subsequently, the order isexecuted on merchant server 40 using information in transaction record54 to run a buy procedure and thus execute a buy process, on merchantserver 40. The order is then confirmed on shopping server 20,transaction record 54 is updated and receipt page 60 is generatedshowing the transaction information and confirmation numbers and thelike from merchant server 40. Once again, it is important to note thatproducts can be selected from plural merchant servers 40 and, in such acase, plural buy procedures will be executed and confirmed on therespective merchant servers 40 using the appropriate shopper accountinformation automatically for each merchant server 40.

It can be seen that the purchase procedure discussed above permitsshopping server 20 to act on as an agent behalf of the shopper ininteractions with merchant servers 40. However, some merchants do notfeel comfortable with shoppers using an agent Web site. In particular,many merchants rely on advertising, affiliate programs, and the like intheir business model and thus can only accomplish their businessobjective if the shopper “visits”, i.e. directly views, their Web siteand its buy pages in particular during shopping. Accordingly, a proxyserver mode of shopping server 20 can be used to offer many of theadvantages of the integrated purchasing procedure disclosed above, whilesatisfying vendors that desire to have the shopper visit their Web sitebuy pages.

Internet proxy servers are well known. The phrase “proxy server” refersgenerally to a server that sits between a client application, such as aWeb browser, and a Web server to intercept requests. The proxy serverthen serves up substantially the same content as the Web server to whichthe request was directed while also performing an auxiliary functionsuch as filtering data, monitoring data, or serving up a cached copy ofthe Web page. In the preferred embodiment, this general concept isexpanded and applied to an integrated shopping environment. In proxyserver mode, parallel secure connections 32 are set up between clientcomputer and shopping server 20 and between shopping server 20 andmerchant server 40, as illustrated in FIG. 2. The first phase of thepurchase procedure is accomplished in the same manner as described abovewith respect to the standard mode. To utilize proxy server mode,merchant database 28 preferably includes form maps for mapping fields inthe order forms of merchant server 40 to fields in shopper database 26.An external editing tool can be provided to develop the form maps in aknown manner. For example, the editing tool can be configured to readthe HTML forms and parse out the data fields. These data fields can thenbe correlated to corresponding fields in custom database 28.

During second phase of the purchasing procedure, when client computer 12requests a Web page from merchant server 40, shopping server 20 (inproxy server mode) handles the request and filters out the HREFs, i.e.HTML document references, and POSTs, i.e. HTML form submissions, topoint to shopping server 20 instead of merchant server 40. When merchantserver 40 sends a blank form to client server 12, the form isintercepted by shopping server 20 and the form is filled out withinformation from shopper database 26. When client computer 12 posts aform back to merchant server 40, shopping server 20 reproduces the postkeeping intact all changes in the form content made by the shopper.First cookie 29 and the second cookie 18 track the sessions as describedabove.

In proxy server mode, when the shopper selects a buy button fromconfirmed page 58 or another page displayed on client computer 12, theshopping cart page, or other buy page, of merchant server 40 isdisplayed. The shopper manually executes the buy procedure of merchantsever 40 using the interface of merchant server 40 as displayed onclient computer 12. This manual procedure is accomplished for eachmerchant server 40 requiring the proxy mode. Accordingly, in proxyserver mode, the shopper views all the buy pages and executes the buyprocedures on merchant server 40. However, shopping server 20 mediatesand assists in filling out forms. Other aspects of the purchaseprocedure using proxy server mode can be similar to the purchaseprocedure described above without proxy server mode.

The invention facilitates on-line commerce by permitting an integratedbuying experience from plural merchants. The invention can beimplemented over any type of communications channel, such as theInternet, a local area network (LAN), a wide area network (WAN), directcomputer connections, or the like, using any type of communicationhardware and protocols. Any type of hardware or combination of hardwarecan be used for the various clients and servers. Accordingly, the term“computer” as used herein, refers to any type of computing device ordata terminal, such as a personal computer, a portable computer, a dumbterminal, a thin client, a hand held device, a wireless phone, or anycombination of such devices. The various clients and servers can be asingle computer at a single location or multiple computers at a singleor multiple locations. For example a server may be comprised of aplurality of redundant computers disposed in co-location facilities atvarious locations to facilitate scalability. Any appropriate server orclient software can be used and any communication protocols can be used.Communication can be accomplished over electric cable, fiber opticcable, any other cable, or in a wireless manner using radio frequency,infrared, or other technologies. Any interface can be used for selectingproducts for purchase. The various information can be stored in anyformat and thus the term “database” as used herein refers to anycollection of information such as a database file, a lookup table, orthe like.

The invention has been described through a preferred embodiment. Howevervarious modifications can be made without departing from the scope ofthe invention as defined by the appended claims and legal equivalents.

What is claimed is:
 1. A method of effecting commerce in a networkedcomputer environment comprising the steps of: identifying a user of aclient computer to a shopping server having a database; selecting aproduct, based on product information in the database, for purchase froma merchant server that is remote from the shopping server; verifying theproduct information related to the selected product selected in saidselecting step by communicating updated information related to theselected product from the merchant server to the shopping server;presenting verified product information verified in said verifying stepto the user for confirmation of a purchase; and executing a buyprocedure on the merchant server for purchase of the selected productsfrom the merchant server if the user confirms the purchase.
 2. A methodas recited in claim 1, wherein the database comprises a product databasehaving product information and a shopper database having shopperinformation.
 3. A method as recited in claim 2, further comprising thesteps of: checking if there is account information in the shopperdatabase related to the user for the merchant server; establishing anaccount related to the user with the merchant server if said checkingstep indicates that there is not account information in the shopperdatabase related to the user for the merchant server; and wherein saidexecuting step comprises executing a buy procedure on the merchantcomputer in association with the account information related to the userfor the merchant server.
 4. A method as recited in claim 2, furthercomprising displaying a buy form to the user containing information fromthe shopper database corresponding to the user and to be used in the buyprocedure.
 5. A method as recited in claim 2, wherein said executingstep comprises manually executing a buy procedure of the merchant serverthrough an interface of the merchant server.
 6. A method as recited inclaim 5, wherein said executing step further comprises filtering outform submissions sent by the merchant server and filling in the filteredforms with information related to the user from the shopper database. 7.A method as recited in claim 1, wherein said selecting step comprisesselecting products for purchase from plural merchant servers and saidexecuting step comprises executing buy procedures of each of the pluralmerchant servers.
 8. A method as recited in claim 1, wherein saidverifying step comprises accessing a checkout page of the merchantserver and downloading the product information related to the selectedproduct from the checkout page.
 9. A method as recited in claim 1,further comprising the steps of: establishing a first cookie on theshopping server containing a merchant server session identification;establishing a second cookie on the client computer identifying a usersession between the client computer and the shopping servercorresponding to the merchant serve identification; and correlating thesecond cookie with a transaction record established in connection withthe first cookie.
 10. A method as recited in claim 1, further comprisingthe steps of: spawning a buy process in the shopping server foraccomplishing said selecting step; and updating a transaction recordbased on the status of the buy process.
 11. A method as recited in claim1, wherein said executing step comprises automatically executing apurchase procedure on the shopping server, the buy procedure of themerchant server being integrated into the purchase procedure.
 12. Acomputer architecture for effecting commerce in a networked environmentcomprising: a client computer; a shopping server executing an agentserver application, said shopping server including a memory devicehaving a database stored therein; a merchant server executing a commerceserver application and being remote from said shopping server; and acommunication channel coupling said merchant server with said shoppingserver and said shopping server with said client computer; wherein, saidagent server application is operative to permit the user of said clientcomputer to select a product based on product information in saiddatabase for purchase from said merchant server, verify the productinformation related to the selected product by requesting updatedinformation related to the selected product from said merchant serverover said communication channel, present verified product information tothe user for confirmation of a purchase, and execute a buy procedure onsaid merchant server for purchase of the selected products from saidmerchant server if the user confirms the purchase.
 13. An architectureas recited in claim 12, wherein said agent server application isoperative to identify the user of said client computer.
 14. Anarchitecture as recited in claim 12, wherein said database comprises aproduct database having product information and a shopper databasehaving shopper information.
 15. An architecture as recited in claim 14,wherein said agent server application is operative to check if there isaccount information in said shopper database related to the user forsaid merchant server, establish an account related to the user with saidmerchant server if there is not account information in said shopperdatabase related to the user for said merchant serve, and execute a buyprocedure on said merchant computer in association with the accountinformation related to the user for said merchant server.
 16. Anarchitecture as recited in claim 14, wherein said agent serverapplication is operative to display a buy form to the user containinginformation from the shopper database corresponding to the user and tobe used in the buy procedure.
 17. An architecture as recited in claim12, wherein said agent server application is operative to permit theuser to manually execute a buy procedure of said merchant server throughan interface of said merchant server.
 18. An architecture as recited inclaim 17, wherein said agent server application is operative to filterout form submissions sent by said merchant server and fill in thefiltered forms with information related to the user from said shopperdatabase.
 19. An architecture as recited in claim 12, wherein said agentserver application is operative to allow the user to select products forpurchase from plural of said merchant servers and execute buy proceduresof each of said plural merchant servers.
 20. An architecture as recitedin claim 12, wherein said agent server application is operative toaccess a checkout page of said merchant server and download the productinformation related to the selected product from the checkout page. 21.An architecture as recited in claim 12, wherein said agent serverapplication is operative to establishing a first cookie on said shoppingserver containing a merchant server session identification, establish asecond cookie on said client computer identifying a user session betweensaid client computer and said shopping server corresponding to themerchant serve identification, and correlate the second cookie with atransaction record established in connection with the first cookie. 22.An architecture as recited in claim 12, wherein said agent serverapplication includes a main process operative to spawn a buy process foraccomplishing selection of products and update a transaction recordbased on the status of the buy process.
 23. An architecture as recitedin claim 12, wherein said agent server application is operative toautomatically execute a purchase procedure on said shopping server, thebuy procedure of said merchant server being integrated into the purchaseprocedure.
 24. An architecture as recited in claim 12, wherein saidcommunication channel comprises the Internet.